Currently I do not really plan to extend this program, as it does exactly what I want it to do, in reasonably fast way.
However, missing keywords for Java and C++ should be included sometimes, and there should be an auto-detection which keyword table to use.
The manual should get some sections describing some internals, what tools can be useful together with vahunz and some ideas to extend the general concept of vahunzation which are beyond this particular tool.
Obvious extensions could be to support other programming languages. However, this would make the source much more error prone, so at the moment I do not think this is a good idea. But I guess Oberon, Modula-2 and Pascal will be supported sometimes - if there is any interest.
Another feature could be to display some statistics about how many names have been replaced etc.; but actually nobody really cares about that, so it's something for a rainy weekend.
Maybe if there is some interest, I release the source code, so you can compile it under other systems, too - it's mostly ANSI-C, with some stuff to create directories. But currently I'm too lazy to put the source directory and the Makefile in a state it is useful for anybody else than me. Of course, a potential source release will be vahunzed. As I had some bad experiences (apparently) in the past with source releases, this is not very likely at the moment.
--line
.
--no-warning
.
--random-seed
.
--store
.
\n
) if a formfeed
(\f
) occurred. Now the formfeed is kicked out.
--help
.
malloc()
s.
DEBUG=LINE
, resulting in a shorter binary.
--quiet
has -q
as short form.